It seems to work most of the time, there is a bug I found out while testing (explained later).

The first commit factors out code from ReleaseCommand._get_consumer_release() into a new get_consumer_release() helper, using it also in the dnf plugin; then the second commit stops using get_consumer_release() in the dnf plugin, leaving this helper used only by its original user (ReleaseCommand._get_consumer_release()). Since these changes are not actually needed for the changes in the dnf plugin, then I'd suggest to simplify the changes in this PR:

• squash the first and the second commit together, since it is enough one commit to change the dnf plugin
• drop the changes in src/subscription_manager/cli_command/release.py and src/subscription_manager/release.py altogether

I tried to first --set a release, then --unset it; the releaseVer attribute of the consumer is now an empty string:

# cat /var/lib/rhsm/cache/releasever.json ; echo
{"releaseVer": ""}

this results in the following output:

# dnf update
Updating Subscription Management repositories.

This system has release set to  and it receives updates only for this release.

Last metadata expiration check: 0:09:54 ago on Wed Mar 27 06:36:24 2024.
[...]

ReleaseCommand.show_current_release() handles both None and empty:

So most likely the dnf plugin ought to do that too; i.e.

                    if release_version is not None:

into

                    if release_version:

Thanks!

thanks!